\pard\tx960\tx1920\tx2880\tx3840\tx4800\tx5760\tx6720\tx7680\tx8640\tx9600\f2\b0\i0\ul0\fs28 UUCP uucico bus error no messages\
\
Q: I'm running
\b uucico
\b0 and all I get is "bus error" -- no other messages, even with debugging turned on to any level. What might be wrong?\
\
A: Ensure that the
\b uucico
\b0 program can access the UUCP spool directory. Since the program is (supposed to be) SetUID uucp and SetGID daemon, this means the uucp user must be able to read and write the directory.\
\
If you examine the files using the UNIX
\b ls
\b0 (1) command, you should see the following (dates might be different, and the size of the spool directory might be different):\
\b0 will be the same whether the owner and the group have execute permission or not. In UNIX parlance, the mode display in the
\b ls
\b0 will be the same whether the numeric mode is 6001, 6011, or 6111. Be
\i sure
\i0 it's 6111: SetUID, SetGID, and execute for user, group, and other.\
\
By the way, the rest of the commands in the UUCP suite are likely subject to the same limitations. We have verified that
\b uucp
\b0 behaves like
\b uucico
\b0 in this situation; we have not tested the rest of the suite, but anything which needs access to the spool directory are suspect. For completeness, here's another
